X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C869D2.CB066316@onstor-exch02.onstor.net>; Thu, 7 Feb 2008 13:45:45 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C869D2.CB066316"
Content-class: urn:content-classes:message
Subject: RE: sc interface state
Date: Thu, 7 Feb 2008 13:45:45 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08350914@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E083508AF@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: sc interface state
Thread-Index: Achpx45J4a326cGNQBun/aoAYFfobgABKBsgAAGmTtA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E0835086F@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E083508AF@onstor-exch02.onstor.net>
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Charissa Willard" <charissa.willard@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>
Cc: "dl-Design Review" <dl-designreview@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C869D2.CB066316
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I concur.


> _____________________________________________=20
> From: 	Charissa Willard =20
> Sent:	Thursday, February 07, 2008 1:01 PM
> To:	Tim Gardner
> Cc:	dl-Design Review
> Subject:	RE: sc interface state
>=20
> Tim,
>=20
> I believe the state should be persistent, too. One bug related to this
> issue is TED00018877 (The second SSC interface sc2 is showing
> Operation column "up" with out connecting cable.)
>=20
> -Charissa
>=20
> _____________________________________________
> From: Tim Gardner=20
> Sent: Thursday, February 07, 2008 12:25 PM
> To: dl-Design Review
> Subject: sc interface state
>=20
> The 'interface modify <name> -s enable' and 'interface modify <name>
> -s disable'
> commands are currently used to enable/disable sc and fp network
> interfaces.
> However, the state of the sc interfaces is not currently persistent.
> If you disable an sc interface and
> then reboot, the interface will be always be configured up if there is
> an IP address configured.
>=20
> Is this the desired behavior or is this a defect?
>=20
> I believe that the state should be persistent as it is for the fp
> interfaces.
> Unless I hear otherwise, I am going to change this as part of another
> sc interface defect I am working on.
>=20
> Tim
>=20

------_=_NextPart_001_01C869D2.CB066316
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: sc interface state</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">I concur.</FONT>
</P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Charissa Willard&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Thursday, February 07, 2008 1:01 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Tim Gardner</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">dl-Design Review</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: sc interface state</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Tim,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">I believe the state should be =
persistent, too. One bug related to this issue is TED00018877 (The =
second SSC interface sc2 is showing Operation column &quot;up&quot; with =
out connecting cable.)</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">-Charissa</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tim Gardner<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, February 07, 2008 12:25 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Design Review<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> sc interface state</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The &#8216;interface modify =
&lt;name&gt; -s enable&#8217; and &#8216;interface modify &lt;name&gt; =
-s disable&#8217;</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">commands are currently used to =
enable/disable sc and fp network interfaces.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">However, the state of the sc =
interfaces is not currently persistent. If you disable an sc interface =
and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">then reboot, the interface will be =
always be configured up if there is an IP address configured.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is this the desired behavior or is this =
a defect?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I believe that the state should be =
persistent as it is for the fp interfaces.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Unless I hear otherwise, I am going to =
change this as part of another sc interface defect I am working =
on.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tim</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C869D2.CB066316--
